Special Notice: In EP 770 (Sub-No. 1) the Board directed all seven (7) Class I rail carriers to submit to the Board two broad categories of data for rail service and employment for a six-month period to better assess how these carriers are performing amid a challenging supply chain environment in light of recent acute service issues. On October 28, 2022, the Board directed carriers to continue data submissions for a six-month period ending May 5, 2023, in light of continued issues. On May 2, 2023, the Board directed Class I carriers to continue weekly performance data and monthly employment data submissions until December 31, 2023, and modified reporting requirements for CSX Transportation, Inc. The Board’s decisions requiring the temporary data submissions are available here, here, here, and here. These new data measures are outlined below.
Click the link to jump to Urgent Issues Rail Service Data.
For Urgent Issues Employment Data, click here.
The Surface Transportation Board requires Class I rail carriers to provide weekly reports containing data on rail service performance. These reports, which also include data pertaining to the Chicago gateway, allow both the agency and the public to have greater real-time visibility into the performance of the Class I industry. The weekly reports filed by the Class I rail carriers can be found below. In addition to the individual carrier reports, the Board has created a spreadsheet of consolidated service performance data for all Class I rail carriers.
Note: The Board issued a final rule in Petition for Rulemaking to Amend 49 C.F.R. Part 1250, Docket No. EP 724 (Sub-No. 5), amending its railroad performance data reporting rules to include certain chemical and plastics traffic as a distinct reporting category to the Class I railroads’ weekly reporting for the “cars-held” metric. The final rule is available here.
Please be advised that Union Pacific Railroad Company (UPRR) restated its weekly data for the “Trains Held” metric, 49 C.F.R. 1250.2(a)(5), for weeks 1 through 14 of 2024 in order to achieve consistency with UPRR’s historical approach to reporting data for this metric. UPRR’s reporting for week 15 of 2024 and going forward will be consistent with its historical approach. An individual weekly file containing the restated “Trains Held” data has been uploaded for each respective reporting week. The consolidated spreadsheet for All Class I Railroads has been updated to incorporate UPRR’s restated weekly data.
BNSF recently noted an error in their data. Table for item #7 (grain loadings) recorded some very occasional grain shipments that were waybilled to Alaska reflecting unusual but real-world routing. When this happened, it would get pulled in their old query and it would shift the data in this table off one cell. BNSF has adjusted their data query so that this issue can no longer occur and the reporting for the identified states is accurate. These changes are now reflected in the updated individual files for the following dates (04/17/2019, 05/01/2019, 05/15/2019, 05/22/2019, 06/17/2020, 07/22/2020, 09/30/2020), as well as the consolidated file starting December 17, 2020.
As of November 11, 2020, the Chicago Terminal weekly report will no longer include data for terminal forecast indicators cars enroute (through no I/C) and subtotal no I/C field. It was determined that data for cars enroute (through no I/C) cannot be collected at this time. Accordingly, those two fields will no longer be included in the weekly report.
Beginning with the report filed with the Board on October 14, 2020, KCSR adjusted its methodology to capture all northbound cars for purposes of calculating Laredo Yard average dwell. This more complete data results in a reduction in weekly average dwell in the Laredo Yard terminal. KCSR noticed in September that the weekly average terminal dwell figure for Laredo Yard reported in Item 2 did not match KCSR’s other observations of dwell in that yard. After researching the issue, KCSR determined that dwell for northbound cars was not being captured correctly because northbound cars were identified as being received by KCSR at the International Bridge but as departing from Laredo Yard, and because those points are separate stations, the cars did not register as dwelling at the Laredo Yard station.
Month | Week 1 | Week 2 | Week 3 | Week 4 | Week 5 |
---|---|---|---|---|---|
May | 05-01-24.xlsx |
Month | Week 1 | Week 2 | Week 3 | Week 4 | Week 5 |
---|---|---|---|---|---|
May | 05-01-24.xlsx | ||||
Apr | 04-03-24.xlsx | 04-10-24.xlsx | 04-17-24.xlsx | 04-24-24.xlsx | |
Mar | 03-06-24.xlsx | 03-13-24.xlsx | 03-20-24.xlsx | 03-27-24.xlsx | |
Feb | 02-07-24.xlsx | 02-14-24.xlsx | 02-21-24.xlsx | 02-28-24.xlsx | |
Jan | 01-03-24.xlsx | 01-10-24.xlsx | 01-17-24.xlsx | 01-24-24.xlsx | 01-31-24.xlsx |
Month | Week 1 | Week 2 | Week 3 | Week 4 | Week 5 |
---|---|---|---|---|---|
May | 05-01-24.xlsx | ||||
Apr | 04-03-24.xlsx | 04-10-24.xlsx | 04-17-24.xlsx | 04-24-24.xlsx | |
Mar | 03-06-24.xlsx | 03-13-24.xlsx | 03-20-24.xlsx | 03-27-24.xlsx | |
Feb | 02-07-24.xlsx | 02-14-24.xlsx | 02-21-24.xlsx | 02-28-24.xlsx | |
Jan | 01-03-24.xlsx | 01-10-24.xlsx | 01-17-24.xlsx | 01-24-24.xlsx | 01-31-24.xlsx |
Month | Week 1 | Week 2 | Week 3 | Week 4 | Week 5 |
---|---|---|---|---|---|
May | 05-01-24.xlsx | ||||
Apr | 04-03-24.xlsx | 04-10-24.xlsx | 04-17-24.xlsx | 04-24-24.xlsx | |
Mar | 03-06-24.xlsx | 03-13-24.xlsx | 03-20-24.xlsx | 03-27-24.xlsx | |
Feb | 02-07-24.xlsx | 02-14-24.xlsx | 02-21-24.xlsx | 02-28-24.xlsx | |
Jan | 01-03-24.xlsx | 01-10-24.xlsx | 01-17-24.xlsx | 01-24-24.xlsx | 01-31-24.xlsx |
Month | Week 1 | Week 2 | Week 3 | Week 4 | Week 5 |
---|---|---|---|---|---|
May | 05-01-24.xlsx | ||||
Apr | 04-03-24.xlsx | 04-10-24.xlsx | 04-17-24.xlsx | 04-24-24.xlsx | |
Mar | 03-06-24.xlsx | 03-13-24.xlsx | 03-20-24.xlsx | 03-27-24.xlsx | |
Feb | 02-07-24.xlsx | 02-14-24.xlsx | 02-21-24.xlsx | 02-28-24.xlsx | |
Jan | 01-03-24.xlsx | 01-10-24.xlsx | 01-17-24.xlsx | 01-24-24.xlsx | 01-31-24.xlsx |
Month | Week 1 | Week 2 | Week 3 | Week 4 | Week 5 |
---|---|---|---|---|---|
Dec | 12-10-14.pdf 12-10-14.xlsx |
12-17-14.pdf 12-17-14.xlsx |
12-23-14.pdf 12-23-14.xlsx |
12-31-14.pdf 12-31-14.xlsx |
|
Nov | 11-05-14.pdf 11-05-14.xlsx |
11-12-14.pdf 11-12-14.xlsx |
11-19-14.pdf 11-19-14.xlsx |
11-26-14.pdf 11-26-14.xlsx |
|
Oct | 10-22-14.pdf 10-22-14.xlsx |
10-29-14.pdf |
Month | Week 1 | Week 2 | Week 3 | Week 4 | Week 5 |
---|---|---|---|---|---|
May | 05-01-24.xlsx | ||||
Apr | 04-03-24.xlsx | 04-10-24.xlsx | 04-17-24.xlsx | 04-24-24.xlsx | |
Mar | 03-06-24.xlsx | 03-13-24.xlsx | 03-20-24.xlsx | 03-27-24.xlsx | |
Feb | 02-07-24.xlsx | 02-14-24.xlsx | 02-21-24.xlsx | 02-28-24.xlsx | |
Jan | 01-03-24.xlsx | 01-10-24.xlsx | 01-17-24.xlsx | 01-24-24.xlsx | 01-31-24.xlsx |
Month | Week 1 | Week 2 | Week 3 | Week 4 | Week 5 |
---|---|---|---|---|---|
Dec | 12-03-14.pdf 12-03-14.xlsx |
12-10-14.pdf 12-10-14.xlsx |
12-17-14.pdf 12-17-14.xlsx |
12-23-14.pdf 12-23-14.xlsx |
12-30-14.pdf 12-30-14.xlsx |
Nov | 11-05-14.pdf 11-05-14.xlsx |
11-12-14.pdf 11-12-14.xlsx |
11-19-14.pdf 11-19-14.xlsx |
11-26-14.pdf 11-26-14.xlsx |
|
Oct | 10-22-14.pdf 10-22-14.xlsx |
10-29-14.pdf | |||
Aug |
Month | Week 1 | Week 2 | Week 3 | Week 4 | Week 5 |
---|---|---|---|---|---|
May | 05-01-24.xlsx | ||||
Apr | 04-03-24.xlsx | 04-10-24.xlsx | 04-17-24.xlsx | 04-24-24.xlsx | |
Mar | 03-06-24.xlsx | 03-13-24.xlsx | 03-20-24.xlsx | 03-27-24.xlsx | |
Feb | 02-07-24.xlsx | 02-14-24.xlsx | 02-21-24.xlsx | 02-28-24.xlsx | |
Jan | 01-03-24.xlsx | 01-10-24.xlsx | 01-17-24.xlsx | 01-24-24.xlsx | 01-31-24.xlsx |
Month | Week 1 | Week 2 | Week 3 | Week 4 | Week 5 |
---|---|---|---|---|---|
May | 05-01-24.xlsx | ||||
Apr | 04-03-24.xlsx | 04-10-24.xlsx | 04-17-24.xlsx | 04-24-24.xlsx | |
Mar | 03-06-24.xlsx | 03-13-24.xlsx | 03-20-24.xlsx | 03-27-24.xlsx | |
Feb | 02-07-24.xlsx | 02-14-24.xlsx | 02-21-24.xlsx | 02-28-24.xlsx | |
Jan | 01-03-24.xlsx | 01-10-24.xlsx | 01-17-24.xlsx | 01-24-24.xlsx | 01-31-24.xlsx |
On November 30, 2016, the Board adopted a final rule to establish new regulations requiring all Class I railroads and the Chicago Transportation Coordination Office, through its Class I members, to report certain rail service performance metrics on a weekly, semiannual, and occasional basis. The primary purpose of the rulemaking was to develop a set of performance data that would allow the STB and stakeholders to monitor current service conditions in the industry.
This data can be used to monitor current service conditions in the rail industry and to identify regional or national service disruptions more quickly. It can benefit rail shippers and other stakeholders by helping them to better plan operations and make informed decisions based on publicly available, near real-time data, and their own analysis of performance trends over time.
The railroads are required to submit the data every Wednesday by the close of business. The data is then posted each Thursday by close of business. Updates will be provided in the Rail Service Data page if there are any delays with the data posting process.
The STB publishes the individual service reports provided by the railroads along with the Chicago Transportation Coordination Office performance reports. The STB creates an additional report by consolidating all the data provided in the individual and CTCO reports.
The following formats are available in the STB rail service page: XLSX, PDF. In addition, USDA created a dashboard with data analytics/visualizations using STB’s rail service data. This can be accessed by creating an account in the USDA website: agtransport.usda.gov/login. Users can also create and embed visualizations directly from USDA’s dashboard. The following data formats are available in the USDA dashboard: CSV, RDF, RSS, TSV, XML.
In EP 770 (Sub-No. 1) the Board directed all seven (7) Class I rail carriers to submit to the Board two broad categories of data for rail service and employment for a six-month period to better assess how these carriers are performing amid a challenging supply chain environment in light of recent acute service issues. On October 28, 2022, the Board directed Class I carriers to continue data submissions for a six-month period ending May 5, 2023, in light of continued issues. On May 2, 2023, the Board directed Class I carriers to continue weekly performance data and monthly employment data submissions until December 31, 2023, and modified reporting requirements for CSX Transportation, Inc. The Board’s decisions requiring the temporary data submissions are available here, here, here, and here. These new data measures are outlined below.
Class I Carrier Data Submission Requirements
The Board required all Class I carriers to submit the following information on a weekly basis for a six-month period beginning on May 18, 2022. On October 28, 2022, the Board directed Class I carriers to continue data submissions for a six-month period ending May 5, 2023, in light of continued issues. On May 2, 2023, the Board directed Class I carriers to continue weekly performance data and monthly employment data submissions until December 31, 2023, and modified reporting requirements for CSX Transportation, Inc.
The weekly data collected in EP 770 are available in the table below. As noted above, the tables reflect the information as submitted by carriers.
Additionally, during the period that carriers are required to submit the data above, the STB will incorporate the data into a weekly service data compilation, along with the service data collected in EP 724. A data dictionary describing the dataset is available here.
The Board directed carriers to file methodology documentation describing the steps taken to calculate certain metrics. The carriers’ methodology documents can be found in their May 18, 2022 filings.
[1] These data augment the system-wide data and the data currently reported here for the ten largest terminals under 49 C.F.R. § 1250.2(a)(5)).
[2] These data augment the weekly average number of trains held per day data currently reported here under 49 C.F.R. § 1250.2(a)(5)), sorted by train type (intermodal, grain unit, coal unit, automotive unit, crude oil unit, ethanol unit, other unit, and manifest).
Who should I contact for questions related to this data?
If you would like to submit an issue or question related to the rail service data in this page, please contact us by calling 202-245-0286, or by emailing .